"No Free/Busy Information Could be Retrieved" ... Exchange 2003
AD 2003 Exchange 2003 Enterprise with SPack 2 Outlook 2003 New AD Domain (single forest, single domain, single domain controller) Newly created user accounts New Exchange server (single server, default everything) Pristine install ... no migrations, no upgrades, built from scratch! Usersget the"No Free/Busy information could be retrieved" when they try to view the schedules of other users.The only solution so far (band-aid with unknown implications!) is to have eachuser create an appointment in their Outlook Calendar as soon as their Outlook is configured ... free/busy information becomes visible after about 10 to 15 minutes.Not only is this tedious (about 130 users), but it can't be the proper solution and may mask or hide the root cause of the problem which in turn will show up as something else later on! I've never seen this before as an organization/domain wide phenomena ... I've seen it now andagain for individual users, but not "straight out of the box"in a new installation. I've spent the last 30 hours reading posts and blogs, but have found nothing that either applies to or fixes the problem. Mostdiscussions are related to migrationto Exchange 2003 or migration from 2003 ... not the situation here. Before you answer, please keep in mind this is an unmodified install of both AD 2003 and XChange 2003. If you don't have the answer to this specific problem, please don't bother to respond, and DON'T try to guess! EHammer
March 19th, 2008 3:57am

Hi, There won't be any free/busy time to view for a user till this user has created something in the calendar and till Outlook has published the calendar info to the schedule + free/busy folder. If you want to have something there for all users send everybody a meeting invitation and have the users accept this invitation. Leif
Free Windows Admin Tool Kit Click here and download it now
March 19th, 2008 10:31pm

I had begun to suspect as such ... I've never seen the problem in the past because all previous installs I've completed were migrations. Sincemigrations includefree/busy (and other public folders) the problem never manifested itself as an enterprise-wide phenomena. Thanks for the response ... too bad MS doesn't have a way of initializing the free/busy in a more "user friendly"manner. It makes me look like an imcompetent to management and has created some awkward conversations especially after I've sold management on the benefits of going all MS and just rebuilding user services and systems! EHammer
March 19th, 2008 11:07pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics